Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1623

reference: 796-tree-1
name: 1623
tree-preservation-order: undefined
796-tpo-1
uprn
address-text
point: POINT (-1.048828 50.858217)
geometry: MULTIPOLYGON (((-1.048729 50.858207,-1.048734 50.858226,-1.048747 50.858244,-1.048769 50.858258,-1.048797 50.858267,-1.048827 50.858271,-1.048858 50.858268,-1.048886 50.858259,-1.048908 50.858245,-1.048923 50.858228,-1.048928 50.858209,-1.048923 50.858189,-1.048910 50.858171,-1.048888 50.858157,-1.048860 50.858148,-1.048830 50.858145,-1.048799 50.858148,-1.048771 50.858156,-1.048749 50.858170,-1.048734 50.858188,-1.048729 50.858207)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL